Usecase Diagram | System Design | Online Banking System
A use case diagram visually represents the system’s functionality through actors (users, administrators) and their interactions with the system. It showcases various use cases consisting of account creation, payment initiation, and also access to the transaction history.
In the above diagram:
- To use the services provided by the bank, a customer must first create an account. For every new customer, the bank confirms the information and opens a new account. The online banking system’s Add Account capability is Use-Case, and each customer is an actor in the Use-Case Diagram.
- Every customer has the ability to view their account balance and request an account transfer across different Bank offices. A cashier is a bank employee that assists with customer service.
- Customers can carry out cash transactions in which they must either take cash from their account or add cash value to their bank account. To properly complete one or more transactions, one of the two—credit or debit cash—or both may be used.
- Customers may or may not choose to get details for further action following each successful transaction. To verify and validate information, the manager might examine the interest value for every account linked to the transaction.
- A consumer may also apply for a loan at a bank, but they must include all necessary information in their loan request.
- The consumer must specify the kind of loan that best suits their needs and goals, as well as the length of time they want to pay it back.
- The management of each bank branch is free to reject loan requests based on terms and circumstances or to accept and approve the loan to start the procedure.
- The bank keeps records for every employee, and the bank oversees every employee in every bank branch. Each branch manager is free to decide whether to give bonuses to staff members. Keep in mind that while all employees receive compensation as part of staff management, not all employees will receive bonuses or promotions.
System Design | Online Banking System
In the digital era, the layout of a Online Banking System is a critical element of any commercial enterprise, it not only affects user experience but also the growth of a service-providing company. This article explores the comprehensive guide to designing a Online Banking System for its efficient use. From practical and non-useful requirements to low-level and High-level design, we’ll delve into each aspect with a focus on readability and effectiveness.
Table of Content
- Functional Requirements
- Non-Functional Requirements
- Usecase Diagram
- Capacity Estimation
- Low-Level Design
- High-Level Design
- Database Design
- Microservices
- APIs Used in System Design of Online Banking System
- API Code Implementation
- Scalability